home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19970929-19971216
/
000169_news@newsmaster….columbia.edu _Wed Oct 22 19:10:22 1997.msg
< prev
next >
Wrap
Internet Message Format
|
1997-12-15
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id TAA26391
for <kermit.misc@watsun.cc.columbia.edu>; Wed, 22 Oct 1997 19:10:21 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id TAA15569
for kermit.misc@watsun; Wed, 22 Oct 1997 19:10:21 -0400 (EDT)
Path: news.columbia.edu!panix!howland.erols.net!news.mathworks.com!mvb.saic.com!news.eskimo.com!jimo
From: jimo@eskimo.com (Jim Osborn)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: login script beeps unexpectedly
Date: 22 Oct 1997 23:03:47 GMT
Organization: Eskimo North (206) For-Ever
Lines: 44
Message-ID: <62m0oj$a7h$1@eskinews.eskimo.com>
References: <62ejvl$fpk$1@eskinews.eskimo.com> <62ft4g$j94$1@apakabar.cc.columbia.edu> <62h9lb$pbm$1@eskinews.eskimo.com> <62icqn$582$1@apakabar.cc.columbia.edu>
NNTP-Posting-Host: eskimo.com
Xref: news.columbia.edu comp.protocols.kermit.misc:7949
In article <62icqn$582$1@apakabar.cc.columbia.edu>,
Frank da Cruz <fdc@watsun.cc.columbia.edu> wrote:
>OK, let's look at your script more closely:
>
>: >: define eskimo {
>: >: while not defined \%1 {
>: >: askq \%1 {Eskimo Password: }
>: >: }
>: >: :retry
>: >: dial 258-0759
>
>You need an IF FAIL statement here. You don't want the script to keep
>executing if your DIAL command fails.
Agreed; I want it to start over, and it would be cleaner to tell it
that explicitly.
>...
>Ditto. In fact, if this one fails, you can fall through the next test
>and then (since the subsequent INPUTs are also untested), out comes the beep.
>
>: >: xif \find({CLI,,27},\v(input)) { #Start over if toxic modem
>: >: xif \find({@seattle2},\v(input)) {
>: >: echo {Aborting 27,,2}
>: >: goto retry
>: >: }
>: >: }
>: >:...
This is all true, but doesn't address the situation where I watched the
action pass by on my screen, seeing the toxic modem sucessfully
detected, the abort message sucessfully echoed, the beep sounded,
and the dialing process restarted, again and again.
I will clean up those unchecked failure possibilities, but I think
the mystery beep must come from elsewhere. Unfortunately (or is
it really fortunately?:) I don't get offered that awful modem often
enough to test the script at will. I'll try relaxing the xif
conditions to something more frequent and let you know how the
cleanup influences things.
Thanks again,
Jim